an approach for semantic integration of heterogeneous data sources

Integrating data from multiple heterogeneous data sources entails dealing with data distributed among heterogeneous information sources, which can be structured, semi-structured or unstructured, and providing the user with a unified view of these data. Thus, in general, gathering information is challenging, and one of the main reasons is that data sources are designed to support specific applications. Very often their structure is unknown to the large part of users. Moreover, the stored data is often redundant, mixed with information only needed to support enterprise processes, and incomplete with respect to the business domain. Collecting, integrating, reconciling and efficiently extracting information from heterogeneous and autonomous data sources is regarded as a major challenge. In this paper, we present an approach for the semantic integration of heterogeneous data sources, DIF (Data Integration Framework), and a software prototype to support all aspects of a complex data integration process. The proposed approach is an ontology-based generalization of both Global-as-View and Local-as-View approaches. In particular, to overcome problems due to semantic heterogeneity and to support interoperability with external systems, ontologies are used as a conceptual schema to represent both data sources to be integrated and the global view

analysis of the documentation of erp software projects

Abstract Software documentation is a basic component of the software development process and it is very important in all the phases of a software system life cycle. It is plays a very important role from the point of view of both the software engineer and user. Software documentation usually includes textual documentation required by the Software engineering standards, API documentation, Wiki pages and source code comments. Surveys and studies indicate that the documentation is not always available and, if available, only partially addresses the developers' needs, as it is often wrong, incomplete, out-of-date and ambiguous. In the context of ERP – Enterprise Resource Planning, the relevance of the software documentation is even more important due to the complexity of such a kind of software systems and the strategic role they have within operative organizations. This paper focuses on the quality assessment of the documentation of ERP open source systems with the aim of understanding if they include high quality documentation for adequately support anyone want to adopt them and/or executing maintenance activities. Specifically, a quality model is defined and its application to three Open source software system is performed

A Literature Review of Business/IT Alignment Strategies

AbstractIn the last years, the alignment issue was addressed in several researches and numerous methods, techniques and tools were proposed. Indeed, the business and IT performance are tightly coupled, and enterprises cannot be competitive if their business and IT strategies are not aligned. This paper proposes a literature review useful for evaluating different alignment approaches, with the aim of discovering similarity, maturity, capability to measure, model, asses and evolve the alignment level existing among business and technological assets of an enterprise. The proposed framework is applied to analyse the alignment research published in the Information & Management journal and the Journal of Strategic Information Systems, that are the ones that more published on this topic. The achieved evaluation results are presented

Assessing the Impact of Measurement Tools on Software Mantainability Evaluation

n/

Bug Report Quality Evaluation Considering the Effect of Submitter Reputation

n/

How Clones are Maintained: An Empirical Study

Despite the conventional wisdom concerning the risks related to the use of source code cloning as a software development strategy, several studies appeared in literature indicated that this is not true. In most cases clones are properly maintained and, when this does not happen, is because cloned code evolves independently. Stemming from previous works, this paper combines clone detection and co–change analysis to investigate how clones are maintained when an evolution activity or a bug fixing impact a source code fragment belonging to a clone class. The two case studies reported confirm that, either for bug fixing or for evolution purposes, most of the cloned code is consistently maintained during the same co–change or during temporally close co–changes

analyzing the instability of the core components of software projects

n/

Effective Anomaly Detection Using Deep Learning in IoT Systems

Anomaly detection in network traffic is a hot and ongoing research theme especially when concerning IoT devices, which are quickly spreading throughout various situations of people's life and, at the same time, prone to be attacked through different weak points. In this paper, we tackle the emerging anomaly detection problem in IoT, by integrating five different datasets of abnormal IoT traffic and evaluating them with a deep learning approach capable of identifying both normal and malicious IoT traffic as well as different types of anomalies. The large integrated dataset is aimed at providing a realistic and still missing benchmark for IoT normal and abnormal traffic, with data coming from different IoT scenarios. Moreover, the deep learning approach has been enriched through a proper hyperparameter optimization phase, a feature reduction phase by using an autoencoder neural network, and a study of the robustness of the best considered deep neural networks in situations affected by Gaussian noise over some of the considered features. The obtained results demonstrate the effectiveness of the created IoT dataset for anomaly detection using deep learning techniques, also in a noisy scenario

A Design-Oriented Specification Language for defining software requirements

The most common difficulty of requirements elicitation is to define all components and aspects of a project by using the natural language without ambiguities, weak phrases and useless descriptions which make project outlines chaotic. In this paper, we present the Design Oriented Specification Language (DOSLang) that aims at reducing the gap existing among the project stakeholders, which are involved into the requirements specification and comprehension activities. The DOSLang language provides a free-form syntax with the introduction of constructs helping project stakeholders to reducing the ambiguity during definitions, descriptions, todos, actions, constraints and all the other aspects related to requirement definition, without sacrificing the ability of specifying loops and conditional constructs, small sets of data type and multiplicity between 'entities'. The DOSLang compiler is designed to be able to create a common baseline, which the project stakeholders can use during the first phases of the project elicitation. DOSLang is suitable for any kind of project that requires a precise description of all of its aspects. Moreover the language was created keeping the possibility to be used by all people working in a project development: from business people to programmers, including customers

An Empirical Study on the Evolution of Design Smells

The evolution of software systems often leads to its architectural degradation due to the presence of design problems. In the literature, design smells have been defined as indicators of such problems. In particular, the presence of design smells could indicate the use of constructs that are harmful to system maintenance activities. In this work, an investigation on the nature and presence of design smells has been performed. An empirical study has been conducted considering the complete history of eight software systems, commit by commit. The detection of instances of multiple design smell types has been performed at each commit, and the analysis of the relationships between the detected smells and the maintenance activities, specifically due to refactoring activities, has been investigated. The proposed study evidenced that classes affected by design smells are more subject to change, especially when multiple smells are detected in the same classes. Moreover, it emerged that in some cases these smells are removed, and this occurs involving more smells at the same time. Finally, results indicate that smells removals are not correlated to the refactoring activities